fix: continue auth discovery after invalid JSON metadata#2140
Conversation
🦋 Changeset detectedLatest commit: 013ebcb The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/server
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
he-yufeng
force-pushed
the
fix/oauth-metadata-non-json-fallback
branch
from
edf4850 to
c3af4a1
Compare
he-yufeng
force-pushed
the
fix/oauth-metadata-non-json-fallback
branch
from
c3af4a1 to
013ebcb
Compare
|
Added the client patch changeset and force-pushed 013ebcb. Local validation: changeset status shows @modelcontextprotocol/client patch; client auth.test.ts passed with 168 tests; client typecheck and lint passed; git diff --check passed. Pre-push typecheck, build, and lint also passed. |
|
I checked the remaining red job. The failed shard is test/server/cloudflareWorkers.test.ts and the failure is a Miniflare network disconnect while POSTing to the endpoint. This PR only touches the client OAuth metadata fallback path plus its client auth tests, and build, client-conformance, server-conformance, pkg-publish, test (20), test (24), bun, and deno all passed. I don't see a PR-related action item from this failure. |
1 participant
Summary
Fixes #2126
To verify